Fix misuse of STM32MP_METADATA_NAME #101
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When
ENABLE_FLASHLAYOUT_CONFIG_FWUPis disabled (set to 0) thenSTM32MP_METADATA_NAMEvariable will be empty and this causes an endless parsingWARNING:what happens when
STM32MP_METADATA_NAMEis empty, the followingFLASHLAYOUT_PARTITION_ENABLE:${STM32MP_METADATA_NAME}will be justFLASHLAYOUT_PARTITION_ENABLE:which triggers these errors saying that other variants replaces it with other content.
This commit sets the default metadata variable and introduces a new variable to simply tell if it needs to be enabled in the flashlayout or not based on
ENABLE_FLASHLAYOUT_CONFIG_FWUP.This also fixes another line:
ENABLE_FLASHLAYOUT_CONFIG_FWUP ?= "${@bb.utils.contains('MACHINE_FEATURES', 'fw-update', '1', '0', d)}"which was commented and
1is forced.